Managing service provider messaging

ABSTRACT

A system and method for management of service plan modification information between various service providers and telecommunications-based devices are provided. A service management component manages subscriber and service plan information for processing service plan modification requests from a service provider and a mobile device of a subscriber. The service management component processes updated service plan information provided by a service provider component and dynamically offers the updated services to subscribers. The service management component also enables subscribers to modify aspects of their service plans and have the modifications take effect immediately. The service management component maintains various data stores associated with subscriber information and service plan information that facilitate the offer of updated service plans, including service plan features and rule sets, received from a service provider component to subscribers at corresponding mobile devices. The service management component manages a framework that allows management of the updated service plan information.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of U.S. patent application Ser. No.12/910,724, filed Oct. 22, 2010, and entitled “Managing Service ProviderMessaging,” which claims the benefit of U.S. Provisional PatentApplication No. 61/362,230, entitled “Managing Service ProviderMessaging,” and filed on Jul. 7, 2010, the entireties of which areincorporated by reference herein.

BACKGROUND

Generally described, computing devices and communication networksfacilitate the collection and exchange of information. Utilizing acommunication network and relevant communication protocols, a computingdevice can engage in data communications with a wide variety ofcomputing devices. In accordance with a telecommunications-basedenvironment, telecommunications-based devices, such as mobile terminals,establish communications with various computing devices via a wirelesscommunication network provided by a wireless communication serviceprovider.

In one embodiment, users associated with a telecommunications-baseddevice can manage one or more services provided by the wirelesscommunication service provider. For example, a user may wish to manageinformation associated with a user account, such updating billinginformation, modifying one or more aspects of a wireless service account(e.g., selecting rate plans, upgrading devices, etc.), and the like. Inanother example, a user may wish to access enhanced services provided bythe wireless communication service provider, such as location basedservices, data processing services, etc. In one embodiment, the servicesprovided by the wireless service provider are facilitated throughinteractions between the user of a telecommunications-based device andone or more service provider components via a communication network,such as the Internet.

To facilitate the management of services, a wireless communicationservice provider can maintain a central interface component thatfunctions as an interface between the telecommunications-based devicesand various service provider components, such as an accounting/billingservice provider component, etc. In accordance with this embodiment, thecentral interface component obtains telecommunications-baseddevice-based requests and transmits the requests to an appropriateservice provider component, such as via an established applicationprogram interface (“API”). Based on the processing of the request, theservice provider component returns information to the central interfacecomponent, typically via an established API.

For service requests that require information to be communicated to therequesting telecommunications-based device, a typical central interfacecomponent returns processing codes to the requestingtelecommunications-based device. For example, in the event that an erroroccurs in processing the service request, the requestingtelecommunications-based device would receive an error code from thecentral interface component. In some embodiments, atelecommunications-based device may maintain messaging information thatcan provide a user with additional context as to the received errorcode. However, the amount of messaging information maintained by thetelecommunications-based device can be limited and is not easily updatedby the wireless service provider.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing aspects and many of the attendant advantages of thepresent disclosure will become more readily appreciated as the samebecome better understood by reference to the following detaileddescription, when taken in conjunction with the accompanying drawings,wherein:

FIG. 1 is a block diagram illustrative of a telecommunicationenvironment including a number of mobile devices, a service interfacecomponent, and a number of service provider components;

FIG. 2A is a block diagram illustrative of components of a serviceinterface component;

FIG. 2B is a block diagram illustrative of components of a mobiledevice;

FIG. 3 is a block diagram of the telecommunication environment of FIG. 1illustrating an embodiment for the processing of mobile device servicerequests;

FIG. 4 is a block diagram of the telecommunication environment of FIG. 1illustrating an embodiment for the processing of service request codemapping information by a service interface component;

FIG. 5 is a block diagram illustrative service request code mappinginformation utilized by a service interface component;

FIG. 6 is a flow diagram illustrative of a service request processingroutine implemented by a service interface component; and

FIG. 7 is a flow diagram illustrative of a request code mappingprocessing routine implemented by a service interface component.

THE DETAILED DESCRIPTION

Generally described, aspects of present disclosure relate to themanagement of communications related to telecommunications-baseddevices. In an illustrative embodiment, the present disclosure relatesto the management of messaging information between various serviceproviders and telecommunications-based devices. In one embodiment, aservice interface component manages error code messaging information forprocessing service provider component error codes corresponding to arequest for services from a telecommunications-based device, such as amobile device. The service interface component processes error codeinformation provided by a service provider component and generatesmessaging information to be provided to a user associated with therequesting mobile device. The service interface component maintainsvarious data stores associated with messaging information and error codeinformation that facilitates a mapping of error code informationreceived from a service provider component to messaging information tobe provided to a mobile device. Additionally, the service interfacecomponent manages a framework that allows the management of the mappinginformation.

Although aspects of the present disclosure will be described with regardto an illustrative telecommunication environment and componentinteractions, communication protocols and flow diagrams, one skilled inthe relevant art will appreciate that the disclosed embodiments areillustrative in nature and should not be construed as limiting. Whilethe present disclosure will be described with regard to error codeprocessing information, one skilled in the relevant art will appreciatethat various types of processing information may be managed inaccordance with aspects of the present disclosure. Additionally,although the terms telecommunications-based device or mobile device areused in this document, the terms represent any type of device having acomponent for communicating with one or more other devices via one ormore communication paths. Such communication paths can include wirelesscommunication paths (via infra-red, RF, optical, terrestrial, orsatellite communication media) and wired communication paths. Stillfurther, although the present disclosure references atelecommunications-based device, one skilled in the relevant art willappreciate that a telecommunications-based device may also be referredto as a wireless computing device, a mobile communication device, amobile terminal, or a computing device. Examples of telecommunicationdevices or mobile devices are described below with regard to FIG. 1.Accordingly, reference to a telecommunications-based device or mobiledevice should not be interpreted as including any particularfunctionality or operation not described in the present disclosure.

With reference now to FIG. 1, an embodiment of an illustrativetelecommunication environment 100 will be described. Thetelecommunication environment 100 can include a number oftelecommunications-based devices, such as mobile devices 102, associatedwith users. The mobile devices 102 can correspond to a wide variety ofdevices or components that are capable of initiating, receiving orfacilitating communications over a communication network 108 including,but not limited to, personal computing devices, electronic book readers(e.g., e-book readers), hand held computing devices, integratedcomponents for inclusion in computing devices, home electronics,appliances, vehicles, machinery, landline telephones, network-basedtelephones (e.g., voice over IP (“VoIP”), cordless telephones, cellulartelephones, smart phones, modems, personal digital assistants, laptopcomputers, gaming devices, media devices, and the like. In anillustrative embodiment, the mobile devices 102 include a wide varietyof software and hardware components for establishing communications overone or more communication networks, generally referred to ascommunication network 108, including wireless communication network or awired communication network (not shown). Illustrative components of amobile device 102 will be described in greater detail with regard toFIG. 2B.

With continued reference to FIG. 1, the telecommunication environment100 includes one or more computing devices, generally referred to as aservice interface component 104, in communication with the mobiledevices 102. In an illustrative embodiment, the service interfacecomponent 104 can maintain data, such as in the form of data tables,that facilitate the management of messaging information to be providedto the mobile devices 102. Specifically, in an illustrative embodimentrelated to the management of error messaging information and errorcodes, the service interface component 104 can illustratively maintainone or more messaging data tables and one or more error code mappingtables. Examples of a messaging data table and an error code mappingtable will be described with regard to FIG. 5. Illustrative componentsof a service interface component 104 will be described in greater detailwith regard to FIG. 2A. One skilled in the relevant art will appreciatethat the service interface component 104 is not limited to any specificstructure, architecture, or set of components.

The telecommunication environment 100 also includes a number of serviceprovider components 106 in communication with the service interfacecomponent 104. Illustratively, the service provider components 106provide services to the mobile devices 102 via requests transmitted overthe communication network 108. Such service provider components 106 aresometimes referred to generally as backend systems or backend processes.As previously indicated, examples of the services provided by the one ormore service provider components include, but are not limited to,managing information associated with user accounts, such updatingbilling information, modifying aspects of a wireless service account(e.g., selecting rate plans, upgrading devices, etc.), downloadingsoftware components/applications, and the like. In other examples, theservices provided by the one or more service provider components includelocation based services, identity services, data enhancements services,data processing services, commerce services, and the like.

With reference now to FIG. 2A, illustrative components of a serviceinterface component 104 will be described. As illustrated in FIG. 2A,the service interface component 104 can include an interface component202 for communicating with various components of the telecommunicationenvironment 100. Illustratively, the interface component 202 cancommunicate with one or more mobile devices 102 via establishedprotocols, such as one or more APIs. Likewise, the interface component202 can communicate with one or more service provider components 106 viaestablished communication protocols, such as one or more APIs.Illustratively, the interface component 202 can be configured tocommunication with the service provider components 106 and mobiledevices 102 in accordance with multiple APIs. Although the interfacecomponent 202 is illustrated as a single component, one skilled in therelevant art will appreciate that the service interface component 104may utilize separate components to communicate with different componentsof the telecommunication environment 100.

The service interface component 104 also includes a service providercode processing component 204 for processing service provider requestsfrom a mobile device 102 and forwarding the requests to a correspondingservice provider component 106. The service provider code processingcomponent 204 also processes processing codes, such as error codes,returned from the service provider component 106 and maps the processingcodes to one or more messages. As previously discussed, the serviceinterface component 104 maintains one or more data stores forfacilitating the processing of service requests, managing processingcode information and managing messaging information. Illustratively, theservice interface component 104 includes an error code trackinginformation data store 206 for maintaining mapping information betweenprocessing codes, such as error codes, and messaging information. Theservice interface component 104 also maintains a messaging informationdata store 208 for maintaining messaging information to be provided tomobile devices 102. Although the error code tracking information datastore 206 and the messaging information data store 208 are illustratedas a single data store, one skilled in the relevant art will appreciatethat either data store may be made up of any number of data stores,databases, or files. Additionally, the error code tracking informationdata store 206 and the messaging information data store 208 may beimplemented in a distributed manner via a communication network, such asthe Internet or a private communication network.

One skilled in the relevant art will appreciate that the serviceinterface component 104 and its various components may be implemented bya one or more computing devices, or a computing system. Each of thecomputing devices may include one or more processing units, such as oneor more CPUs. The computing devices may also include system memory,which may correspond to any combination of volatile and/or non-volatilestorage mechanisms. The system memory may store information whichprovides an operating system component, various program components,program data, and other components. The computing devices may alsoinclude one or more input devices (keyboard, mouse device, specializedselection keys, etc.) and one or more output devices (displays,printers, audio output mechanisms, network interfaces, etc.). Thecomputing devices perform functions by using the processing unit(s) toexecute instructions provided by the system memory. The above-enumeratedlist of components is representative and is not exhaustive of the typesof functions performed, or components implemented, by a computingdevice. One skilled in the relevant art will appreciate that additionalor alternative components may also be included in a computing device, orcomputing system made up of one or more computing devices, to carry outother intended function of the service interface component.

With reference now to FIG. 2B, illustrative components of atelecommunication device, such as a mobile device 102, for use in thegeneration of service requests will be described. The mobile device 102may include one or more processing units 202, such as one or more CPUs.The mobile device 102 may also include system memory 204, which maycorrespond to any combination of volatile and/or non-volatile storagemechanisms. The system memory 204 may store information which providesan operating system component 206, various program components 208,program data 210, and other components. The above-enumerated list ofcomponents is representative and is not exhaustive of the types offunctions performed, or components implemented, by the mobile device102. One skilled in the relevant art will appreciate that additional oralternative components may also be included in thetelecommunications-based device 102 to carry out other intendedfunctions such as a mobile telephone functions. The mobile device 102performs functions by using the processing unit(s) 202 to executeinstructions provided by the system memory 204. The mobile device 102may also include one or more input devices 212 (keyboard, mouse device,specialized selection keys, etc.) and one or more output devices 214(displays, printers, audio output mechanisms, etc.).

With continued reference to FIG. 2B, the mobile device 102 may alsoinclude one or more types of removable storage 216 and one or more typesof non-removable storage 218. Still further, the mobile device 102 caninclude communication components 220 for facilitating communication viawired and wireless communication networks, such as the wirelesscommunication network 104 and data network 118 (FIG. 1). Examples ofvarious communication protocols include, but are not limited to,Bluetooth, the family of IEEE 802.11 technical standards (“WiFi”), theIEEE 802.16 standards, short message service (“SMS”), voice over IP(“VoIP”), as well as various generation cellular air interface protocols(including, but not limited to, air interface protocols based on CDMA,TDMA, GSM, WCDMA, CDMA2000, TD-SCDMA, WTDMA, LTE, OFDMA, WiMAX, andsimilar technologies).

Turning now to FIG. 3, a block diagram of the telecommunicationenvironment 100 of FIG. 1 illustrating an embodiment for the processingof mobile device service requests by the service interface component 104will be described. As illustrated in FIG. 3, a mobile device 102transmits a service request to the service interface component 104 viathe communication network 108. The service request may be transmittedvia an established protocol, such as an API. Based on the servicerequest, the service interface component 104 identifies one or moreservice provider components 106 to receive the corresponding servicerequest and transmits the service request to the identified serviceprovider component 106. The transmission of the service request may betransmitted in accordance with an established protocol, such as an API.

The service provider component 106 processes the request and generates aresponse. The response is transmitted to the service interface component104 via an established protocol, such as an API. The response caninclude one or more processing codes, such as error codes, thatcorrespond to the processing of the service request. Illustratively, theprocessing codes can be encompassed as fields or values to be specifiedin the API. In one embodiment, one or more service provider components106 can share a common API for communicating with the service interfacecomponent 104. Alternatively, individual service provider components 106may maintain unique APIs for communicating with the service interfacecomponent 104. Additionally, the response can not have any messaginginformation corresponding to messaging information to be provided to themobile device 102.

Based on the information included in the response from the serviceprovider component 106, the service interface component 104 dynamicallymaps processing code information to at least one messaging identifier.With reference to an error code processing embodiment, the serviceinterface component 104 dynamically maps error codes included in theresponse from the service provider component 106 with a messagingidentifier maintained in the error code tracking data store 206 (FIG.2). The service interface component 104 then dynamically obtainsmessaging information associated with the messaging identifiers, such asfrom the messaging information data store 208 (FIG. 2). The serviceinterface component 104 then transmits the corresponding messaginginformation to the requesting mobile device 102.

With reference now to FIG. 4, a block diagram of the telecommunicationenvironment of FIG. 1 illustrating an embodiment for the processing ofservice request code mapping information by a service interfacecomponent 104 will be described. As illustrated in FIG. 4, a serviceprovider, such as via service provider component 106, transmits servicerequest code mapping information to the service interface component 104.The transmission of the service request code mapping information may bein accordance with an established protocol, such as an API. Examples ofthe service request code mapping information can include, but are notlimited to, the modification of mapping information mapping processingcodes with messaging identifiers, the managing of messaging informationassociated with the messaging identifiers, and the like.

Based on the receipt of the request from the service provider component106, the service interface component 104 processes the requests andmodifies one or more of the data stores. With reference to an error codeprocessing embodiment, the service interface component 104 dynamicallyupdates error codes included in the response from the service providercomponent 106 with a messaging identifier maintained in the error codetracking data store 206 (FIG. 2). The service interface component 104can also dynamically update messaging information associated with themessaging identifiers, such as from the messaging information data store208 (FIG. 2). The service interface component 104 can then optionallytransmit an acknowledgment or confirmation to the requesting serviceprovider component 106. Based on the dynamically updated information,subsequent service requests from mobile devices 102 resulting in thesame processing code will receive the updated messaging informationwithout having to include the messaging information in the response fromthe service provider component 106 or updating the mobile device 102.

With reference now to FIG. 5, a block diagram illustrative of variousinformation utilized by a service interface component 104 for mappingprocessing codes with messaging information will be described. Theinformation includes an illustrative messaging information data table500 for maintaining messaging information. The messaging informationdata table 500 includes a first column 502 for maintaining messagingidentifiers utilized to match message text or other messaginginformation. The messaging identifiers may be unique identifiers suchthat two different messaging information will not have a commonidentifier. For example, if the service interface component 104 ismaintained by a third party service with multiple service providersutilizing the service interface component 104 globally unique messageidentifiers can prevent any type of messaging overlap. Alternatively,one or more of the messaging identifiers may also overlap or have commonsubject matter for sharing messaging information between serviceproviders or within a service provider context. For example, a singlemessaging identifier can be mapped to different language versions ofmessaging information.

With continued reference to the messaging information data table 500,column 504 includes an identification of messaging information to beprovided to a mobile device 102. Although messaging information incolumn 504 is illustrated as textual data, one skilled in the relevantart will appreciate that the messaging information can include othertypes of information, including multi-media information, and the like.In such embodiments, the messaging information data table 500 mayinclude multiple columns mapped to messaging identifiers, or portions ofmessaging identifiers, to message content. For example, a serviceprovider component 106 may not only be able to specify an error code,but perhaps the type of message content (e.g., video vs. text) that willbe transmitted. In another example, a service provider component 106 ormobile device may specify a preferred language for the messaginginformation. With reference to an illustrative example, the messaginginformation data table 500 includes three rows 506, 508, 510 thatcorrespond to messaging information that may be provided by a serviceinterface component 104.

With reference again to FIG. 5, the information utilized by a serviceinterface component 104 for mapping processing codes with messaginginformation also includes a processing code mapping information datatable 550. The processing code mapping information data table 550includes a first column 552 for identifying specific protocols, such asAPIs, that will specify processing codes from a service providercomponent 106. The processing code mapping information data table 550also includes one or more columns for identifying values of theprocessing codes that will be used to map to particular messagingidentifier. As illustrated in FIG. 5, the processing code mappinginformation data table 550 includes a second column 554 for specifyingstatus/message types for the returned API and a third column 556 forspecifying values of the processing code. The specification of thestatus/message type allows the service provider component 106 todistinguish from types of messages or service requests within the sameAPI. However, column 554 may be omitted.

The processing code mapping information data table 550 also includes acolumn 558 for specifying one or more messaging identifiers for thevalues. As illustrated in FIG. 5, rows 560 and 564 specify a singlemessaging identifier for a value returned in an API, “API 1” and “API3”. Rows 562 and 564 specify different messaging identifiers fordifferent values for the same API, “API 2”. Thus, the service interfacecomponent 104 can dynamically map various processing codes to messagingidentifiers and return different message content to a requesting mobiledevice 102.

Turning now to FIG. 6, a flow diagram illustrative of a service requestprocessing routine 600 implemented by a service interface component 104will be described. At block 602, the service interface component 104obtains a service request from a mobile device 102. As previouslydescribed, in an illustrative embodiment, the service request may beobtained via an established communication protocol, such as API. Atblock 604, the service interface component 104 transmits a servicerequest API to an identified service provider component 106. In oneembodiment, the service interface component 104 may identify theappropriate service provider component 106 based on informationmaintained by the service interface component 104. In anotherembodiment, the identification of the particular service providercomponent 106 may be included in the mobile device request.

At block 606, the service interface component 104 obtains a processingcode API from the identified service provider component 106.Illustratively, the processing code API includes a specification of atleast one processing code, such as an error code. The processing codeAPI can also include additional information such as message typeinformation that specifies what type of content should be provided tothe mobile device users (e.g., premium users obtaining enhancedcontent). However, illustratively, the processing code API would notinclude a messaging identifier or messaging content in the information.One skilled in the relevant art will appreciate that service providercomponents 106 can utilize the same APIs or processing code values incommon APIs. Alternatively, each service provider component 106, orgroups of service provider components, can utilize individualized orcustomized APIs or processing code values in common APIs.

At block 608, the service interface component 104 maps the servicerequest processing codes included in the processing code API to identifyone or more applicable messaging identifiers. The mapping of servicerequest processing codes can be dynamic to reflect the most currentupdates to the messaging identifiers. At block 610, the serviceinterface component 104 identifies the messaging content correspondingto the messaging identifiers and transmits the corresponding messagingcontent to the requesting mobile device 102. In an illustrativeembodiment, the service interface component 104 can utilize one or moreadditional information sources to select from multiple, potentiallyapplicable messaging content. For example, the service interfacecomponent 104 can obtain a preferred language for a mobile device userin the event that multiple language versions of the messaging contentare available. In another example, the service interface component 104can obtain other criteria, such as geographic information, timeinformation, account status information associated with the mobiledevice user to facilitate selection of messaging content. For example,the service interface component 104 can select an “after hours” basedmessage for processing codes received after normal business hours.Similarly, the service interface component 104 can select a “delinquentaccount” based message according to an account status associated with amobile device user's account with the service provider. One skilled inthe relevant art will appreciate that additional or alternative criteriamay also be utilized in accordance with the present disclosure. At block612, the routine 600 terminates.

With reference now to FIG. 7, a flow diagram illustrative of a requestcode mapping processing routine implemented by a service interfacecomponent 104 will be described. At block 702, the service interfacecomponent 104 obtains a request corresponding to processing code mappinginformation. As previously described, the request can include anaddition of messaging information or messaging identifiers to amessaging information data store, a modification of mapping informationmapping processing codes to message identifiers in a processing codedata store, and the like. At block 704, the service interface component104 identifies all relevant APIs, processing code values (e.g., errorcode values), and messaging identifiers that may need to be updated.

At block 706, the service interface component 104 updates theappropriate data stores corresponding to the request. At block 708, theroutine 700 terminates.

All of the processes described herein may be embodied in, and fullyautomated via, software code modules executed by one or more generalpurpose computers or processors. The code modules may be stored in anytype of computer-readable medium or other computer storage device. Someor all the methods may alternatively be embodied in specialized computerhardware. In addition, the components referred to herein may beimplemented in hardware, software, firmware, or a combination thereof.As such, reference in the disclosure to actions performed by a module orcomponent relates to the execution of executable instructions by aprocessing device, or devices, to cause the referenced action to bepreformed.

Conditional language such as, among others, “can,” “could,” “might,” or“may,” unless specifically stated otherwise, are otherwise understoodwithin the context as used in general to convey that certain embodimentsinclude, while other embodiments do not include, certain features,elements, and/or steps. Thus, such conditional language is not generallyintended to imply that features, elements, and/or steps are in any wayrequired for one or more embodiments or that one or more embodimentsnecessarily include logic for deciding, with or without user input orprompting, whether these features, elements, and/or steps are includedor are to be performed in any particular embodiment.

Any process descriptions, elements or blocks in the flow diagramsdescribed herein and/or depicted in the attached figures should beunderstood as potentially representing modules, segments, or portions ofcode which include one or more executable instructions for implementingspecific logical functions or elements in the process. Alternateimplementations are included within the scope of the embodimentsdescribed herein in which elements or functions may be deleted, executedout of order from that shown, or discussed, including substantiallyconcurrently or in reverse order, depending on the functionalityinvolved as would be understood by those skilled in the art.

It should be emphasized that many variations and modifications may bemade to the above-described embodiments, the elements of which are to beunderstood as being among other acceptable examples. All suchmodifications and variations are intended to be included herein withinthe scope of this disclosure and protected by the following claims.

1. A computer-implemented method for managing communications comprising:obtaining a request from a mobile device corresponding to a request forprocessing by a service provider; obtaining a response from theidentified service provider component, the response including an errorcode associated with the processing of the request from the mobiledevice; dynamically identifying at least one messaging identifiercorresponding to the error code associated with the processing of therequest from the mobile device from an error code tracking informationdata store, the error code tracking data store mapping error codeinformation to messaging identifiers; dynamically identifying messaginginformation from a messaging information data store according to theidentified at least one messaging identifier and a language preferenceassociated with the mobile device, wherein the messaging information isassociated with at least a messaging identifier; and transmitting theidentified messaging information to the mobile device.
 2. Thecomputer-implemented method as recited in claim 1, wherein the computingdevice is further operative to identify messaging information associatedin accordance with at least one additional selection criteria.
 3. Thecomputer-implemented method as recited in claim 2, wherein theadditional selection criteria include at least one of a geographiccriteria, language criteria, time criteria and account status criteria.4. The computer-implemented method as recited in claim 1 furthercomprising mapping of an error code, a message type and a messagingidentifier.
 5. The computer-implemented system as recited in claim 1,wherein dynamically identifying messaging information from a messaginginformation data store according to the identified at least onemessaging identifier and a language preference associated with themobile device includes dynamically messaging information according to amessage type.
 6. The computer-implemented method as recited in claim 1,wherein obtaining a response from the identified service providercomponent includes obtaining the error code associated with theprocessing of the request from the mobile device in accordance with anapplication protocol interface.
 7. A computer-implemented system formanaging communications, the system comprising: an error code trackingdata store for storing information mapping error code information tomessaging identifiers; a messaging information data store formaintaining messaging information to be provided to mobile device users,the messaging information associated with at least a messagingidentifier; and a computing device in communication with said datastores that is operative to: obtain a request from a mobile devicecorresponding to a request for processing by a service provider; obtaina response from the identified service provider component, the responseincluding an error code associated with the processing of the requestfrom the mobile device; identify at least one messaging identifiercorresponding to the error code associated with the processing of therequest from the mobile device from the error code tracking informationdata store; identify messaging information from the messaginginformation data store according to the identified at least onemessaging identifier and a language preference; transmit the identifiedmessaging information to the mobile device; obtain a request from asecond mobile device corresponding to a request for processing by theservice provider; obtain a response from the identified service providercomponent, the response including the error code associated with theprocessing of the request from the mobile device; identify at least onedifferent messaging identifier corresponding to the error codeassociated with the processing of the request from the mobile devicefrom the error code tracking information data store, the differentmessaging identifier corresponding to a different language preference;identify messaging information from the at least one different messaginginformation data store according to the identified at least onedifferent messaging identifier; and transmit the messaging informationto the second mobile device.
 8. The computer-implemented system asrecited in claim 7, wherein the error code tracking information datastore includes a mapping of an error code, a message type and amessaging identifier.
 9. The computer-implemented system as recited inclaim 7, wherein the computing device is operative to identify messaginginformation from the at least one messaging information data storeaccording to the identified at least one messaging identifier andmessage type.
 10. The computer-implemented system as recited in claim 7,wherein the computing device is operative to identify messaginginformation from the at least one messaging information data storeaccording to the identified at least one messaging identifier.
 11. Thecomputer-implemented system as recited in claim 7, wherein the computingdevice is operative to obtain the response from the identified serviceprovider component including the error code associated with theprocessing of the request from the mobile device in accordance with anapplication protocol interface.
 12. The computer-implemented system asrecited in claim 7, wherein the error code information is not associatedwith a language identifier.
 13. A computer-implemented method formanaging communications comprising: obtaining a request from a mobiledevice corresponding to a request for processing by a service provider;obtaining a response from the identified service provider component, theresponse including an error code associated with the processing of therequest from the mobile device; identifying at least one messagingidentifier corresponding to the error code associated with theprocessing of the request from the mobile device from an error codetracking information data store, the error code tracking data storemapping error code information to messaging identifiers; identifyingmessaging information from a messaging information data store accordingto the identified at least one messaging identifier, wherein themessaging information data store maintaining messaging information to beprovided to mobile device users and wherein the messaging information isassociated with at least a messaging identifier and a languagepreference associated with the mobile device; transmitting the messaginginformation to the mobile device; obtaining a request from a secondmobile device corresponding to a request for processing by the serviceprovider; obtaining a response from the identified service providercomponent, the response including the error code associated with theprocessing of the request from the mobile device; identifying at leastone different messaging identifier corresponding to the error codeassociated with the processing of the request from the mobile devicefrom the error code tracking information data store; identifyingmessaging information from the at least one different messaginginformation data store according to the identified at least onemessaging identifier based on a language preference associated with thesecond mobile device;; and transmitting the messaging information to thesecond mobile device.
 14. The computer-implemented method as recited inclaim 13, wherein the error code tracking information data storeincludes a mapping of an error code, a message type and a messagingidentifier.
 15. The computer-implemented method as recited in claim 13,wherein the computing device is further operative to identify messaginginformation associated in accordance with at least one additionalselection criteria.
 16. The computer-implemented method as recited inclaim 15, wherein the additional selection criteria include at least oneof a geographic criteria, language criteria, time criteria and accountstatus criteria.
 17. The computer-implemented method as recited in claim13 further comprising mapping of an error code, a message type and amessaging identifier.
 18. The computer-implemented method as recited inclaim 13 further comprising obtaining language preference informationfrom at least one of the first mobile device and the second mobiledevice.